Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1532

reference: 166-tree-1
name: 1532
tree-preservation-order: undefined
166-tpo-1
uprn
address-text
point: POINT (-0.940701 50.865613)
geometry: MULTIPOLYGON (((-0.940673 50.865610,-0.940674 50.865616,-0.940678 50.865621,-0.940692 50.865628,-0.940701 50.865629,-0.940709 50.865628,-0.940724 50.865621,-0.940728 50.865616,-0.940729 50.865611,-0.940728 50.865605,-0.940724 50.865600,-0.940718 50.865596,-0.940701 50.865593,-0.940685 50.865596,-0.940678 50.865600,-0.940674 50.865605,-0.940673 50.865610)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL